X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C82C8E.1A26CAA8@onstor-exch02.onstor.net>; Wed, 21 Nov 2007 14:30:21 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C82C8E.1A26CAA8"
Content-class: urn:content-classes:message
Subject: RE: Updated Invisible Share Mini-Functional Spec
Date: Wed, 21 Nov 2007 14:30:21 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E06B7A89D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E06B7A817@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated Invisible Share Mini-Functional Spec
Thread-Index: AcgsArMN/7im2pNFRfiOjtxmGLR1qAAcaiWQAAB62YAAAZTTEAAEXbYA
References: <BB375AF679D4A34E9CA8DFA650E2B04E06B7A489@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E06B7A7D2@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E06B7A7E0@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E06B7A817@onstor-exch02.onstor.net>
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Ron Bhanukitsiri" <ronb@onstor.com>,
	"Joshua Goldenhar" <joshua.goldenhar@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>
Cc: "Narayan Venkat" <narayan.venkat@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C82C8E.1A26CAA8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Exactly.

> _____________________________________________=20
> From: 	Sandrine Boulanger =20
> Sent:	Wednesday, November 21, 2007 12:27 PM
> To:	Ron Bhanukitsiri; Joshua Goldenhar; dl-Design Review
> Cc:	Narayan Venkat
> Subject:	RE: Updated Invisible Share Mini-Functional Spec
>=20
> So in summary:
> Existing shares which end with $ will stay invisible from the client
> side
> New shares which end with $ will be invisible from the client side
> New shares with regular names and no $ at the end created with new -i
> option will be invisible from the client side
>=20
> Correct?
>=20
> _____________________________________________
> From: Ron Bhanukitsiri=20
> Sent: Wednesday, November 21, 2007 11:44 AM
> To: Joshua Goldenhar; dl-Design Review
> Cc: Ron Bhanukitsiri; Narayan Venkat
> Subject: RE: Updated Invisible Share Mini-Functional Spec
>=20
> Thanks Joshua for your input and feedback. =20
>=20
> Initially, we weren't placing any limitations on the hidden share
> (share with $).
> During the review, Jonathan gave this feedback:
> "Looks good to me.  Some minor notes:
> 1.	If the share ends in $ but was explicitly created with the -h
> disabled flag it would be confusing since it really is hidden.
> 2.	If the share ends in $ but was not explicitly created with the
> -h enabled flag it would be confusing if the 'cifs show' command did
> not return that it was in fact hidden."
>=20
> I considered it and happened to agree with Jonathan's point that it's
> confusing.
> Therefore, if the customer wants the share to be totally invisible,
> don't use "$".
> Furthermore, I would like to point back to the PVR that the customer
> does *not*
> seem want the invisible feature and they want to keep the $ share for
> some
> "special purpose".
>=20
> Ron B[ee]
>=20
> _____________________________________________
> From: Joshua Goldenhar=20
> Sent: Wednesday, November 21, 2007 11:37 AM
> To: Ron Bhanukitsiri; dl-Design Review
> Subject: RE: Updated Invisible Share Mini-Functional Spec
>=20
> I like the write up but have a question about the decision to not
> allow an invisible hidden share.
> Why?
>=20
> You state it's an oxymoron scenario yet I don't think it is.
> "Hidden share" functionality is defined/enforced by the client.
> "Invisible Share" is defined/enforced by the Filer (and hence by
> extension, the administrator).
>=20
> In other words, you could have an invisible, hidden share.
>=20
> I give you this scenario:
> An admin has wanted to have some shares be non-browseable so they
> utilized the only option available, naming a share "foo$".
>=20
> Some folks have clients that let them see these shares while browsing,
> like some Linux clients, etc.
> Now we offer this feature which is really what the admin wanted in the
> first place. But because you are not allowing the "foo$" share to be
> set to invisible, the admin is forced to rename the shares if they
> want this functionality.
>=20
> My point is, since invisible shares are being enforced by the server
> and are a function that is outside of CIFS specs, why limit this
> functionality? Shares that end in '$' are just valid share names... It
> also reduces test matrix and code complexity.
>=20
> -Josh
>=20
> Josh Goldenhar
> Phone: 408 963 2408, Cell: 408 547 7693
>=20
> _____________________________________________
> From: Ron Bhanukitsiri=20
> Sent: Tuesday, November 20, 2007 9:52 PM
> To: dl-Design Review
> Cc: Ron Bhanukitsiri
> Subject: Updated Invisible Share Mini-Functional Spec
>=20
> Here's an updated version of the spec.  Please note the feature is now
> called
> "invisible share" to be more conformant with the PVR and also to avoid
> confusion with the hidden share terminology which is a Microsoft
> feature.
> <\\mightydog\software\CIFS\Invisible Share FuncSpec.doc>
>=20
> Also the CLI option has obviously changed as well.
>=20
> Ron B[ee]
>=20

------_=_NextPart_001_01C82C8E.1A26CAA8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Updated Invisible Share Mini-Functional Spec</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Exactly.</FONT>
</P>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Sandrine Boulanger&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Wednesday, November 21, 2007 12:27 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Ron Bhanukitsiri; Joshua Goldenhar; dl-Design =
Review</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Narayan Venkat</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: Updated Invisible Share =
Mini-Functional Spec</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">So in summary:</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Existing shares =
which end with $ will stay invisible from the client side</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">New shares which end =
with $ will be invisible from the client side</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">New shares with =
regular names and no $ at the end created with new &#8211;i option will =
be invisible from the client side</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Correct?</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Ron Bhanukitsiri<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Wednesday, November 21, 2007 11:44 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Joshua Goldenhar; dl-Design Review<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Ron Bhanukitsiri; Narayan Venkat<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Updated Invisible Share Mini-Functional =
Spec</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks Joshua for =
your input and feedback.&nbsp; </FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Initially, we =
weren&#8217;t placing any limitations on the hidden share (share with =
$).</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">During the review, =
Jonathan gave this feedback:</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&#8220;Looks good to =
me.&nbsp; Some minor notes:</FONT>
<UL>
<OL TYPE=3D1>
<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">If the share ends in =
$ but was explicitly created with the &#8211;h disabled flag it would be =
confusing since it really is hidden.</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">If the share ends in =
$ but was not explicitly created with the &#8211;h enabled flag it would =
be confusing if the &#8216;cifs show&#8217; command did not return that =
it was in fact hidden.&#8221;</FONT></LI>
<BR>
</OL></UL>
<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I considered it and =
happened to agree with Jonathan&#8217;s point that it&#8217;s =
confusing.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Therefore, if the =
customer wants the share to be totally invisible, don&#8217;t use =
&#8220;$&#8221;.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Furthermore, I would =
like to point back to the PVR that the customer does *</FONT><B><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">not</FONT></B><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">*</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">seem want the =
invisible feature and they want to keep the $ share for some</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&#8220;special =
purpose&#8221;.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Ron B[ee]</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Wednesday, November 21, 2007 11:37 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Ron Bhanukitsiri; dl-Design Review<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Updated Invisible Share Mini-Functional =
Spec</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I like the write up =
but have a question about the decision to not allow an invisible hidden =
share.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Why?</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">You state it&#8217;s =
an oxymoron scenario yet I don&#8217;t think it is.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&#8220;Hidden =
share&#8221; functionality is defined/enforced by the client.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&#8220;Invisible =
Share&#8221; is defined/enforced by the Filer (and hence by extension, =
the administrator).</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">In other words, you =
could have an invisible, hidden share.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I give you this =
scenario:</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">An admin has wanted =
to have some shares be non-browseable so they utilized the only option =
available, naming a share &#8220;foo$&#8221;.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Some folks have =
clients that let them see these shares while browsing, like some Linux =
clients, etc.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Now we offer this =
feature which is really what the admin wanted in the first place. But =
because you are not allowing the &#8220;foo$&#8221; share to be set to =
invisible, the admin is forced to rename the shares if they want this =
functionality.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">My point is, since =
invisible shares are being enforced by the server and are a function =
that is outside of CIFS specs, why limit this functionality? Shares that =
end in &#8216;$&#8217; are just valid share names&#8230; It also reduces =
test matrix and code complexity.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">-Josh</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Josh Goldenhar</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Phone: 408 963 2408, =
Cell: 408 547 7693</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Ron Bhanukitsiri<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tuesday, November 20, 2007 9:52 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Design Review<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Ron Bhanukitsiri<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> Updated Invisible Share Mini-Functional =
Spec</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Here&#8217;s an updated version of the =
spec.&nbsp; Please note the feature is now called</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&#8220;invisible share&#8221; to be =
more conformant with the PVR and also to avoid</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">confusion with the hidden share =
terminology which is a Microsoft feature.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&lt;</FONT><A =
HREF=3D"file://\\mightydog\software\CIFS\Invisible Share =
FuncSpec.doc"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">\\mightydog\software\CIFS\Invisible Share =
FuncSpec.doc</FONT></U></A><FONT FACE=3D"Times New Roman">&gt;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Also the CLI option has obviously =
changed as well.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Ron B[ee]</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C82C8E.1A26CAA8--
